home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
qbbs
/
qmx_120.zip
/
_NEW_IN_.120
< prev
next >
Wrap
Text File
|
1990-02-27
|
8KB
|
133 lines
Fixes and enhancements in QMX public release 1.20:
1) QMX always displays the filesize of the mailbag before download.
2) QMX no longer allows the user to specify a file pathname on uploads.
Fixes and enhancements in QMX public release 1.10:
0) If you have a large DOS 4.0+ partition and had "Share.Exe" loaded, even
if you weren't really file-sharing, (using QMX beta 1.04) the DOS TCNODE
environment had to be set otherwise you would get random results. It now
assumes node 1, so single-line systems with Share enabled are not treated
like networks (see below for use of TCNODE environment variable - it is
only required for true multi-line systems).
1) New config parameter "BBSID" accepts an 11-character filename (*without*
pathname!) and inserts that file into the mailbags for use with external
routines to manipulate and manage response mailbags according to the BBS
from which it was downloaded. Example: "BBSID EBAYXCHG.XRS". This should
be a *small* file - possibly even zero length or one byte would be OK.
2) "Logoff" parameter for "Proceed with Default...?" question allows users
to snag mail and log off at end with automatic "last read" update. When a
user selects this option, the mailbag is packed, sent, "lastreads" are then
updated, and the user is logged off by dropping DTR. The modem will not
answer again until you have QuickBBS reinitialize it! Using a comm program
with Z-Modem auto-download let's you "go out to lunch" after selecting this
option, since you're automatically disconnected afterwards. Note that this
option is accepted but has little meaning for local logons, except that the
user doesn't want to go back into the BBS. A trio of new exit errorlevels
allows you to detect this condition at exit and act accordingly. As before
the program will exit with zero on no errors or mail moved, 1 if a download
of mailbag occured, 2 if mail was uploaded, 3 if both - plus now 4 indicates
automatic logoff, 5 indicates all download and logoff and 6 indicates all 3
of the above - download, upload and automatic logoff. You should make new
errorlevel 4 through 6 *not* recycle the BBS, but load QuickBBS "fresh" to
wait for a new call, instead of going back to the "after-Door" re-entry QMX
always used before! Note that QMX updates all of the USERS.BBS files and
such so no data is lost. Ed Meloan tells me it really doesn't matter if you
handle this or not - QuickBBS sees the carrier missing and recycles anyway.
3) The MSGTOIDX.BBS is correctly fixed. I never used (even opened) this file
before, but Steve Gabrilowitz informs me that it's the reason why things
didn't look like you had read a message until you ran the "MSGPACK" utility
nightly (even though I *was* properly marking the individual MSGHDR.BBS
record "read" all along) . This should work correctly now! (since the
"MSGTOIDX.BBS" file isn't documented at all in STRUCT.261 - how should I
know about these things? <grin>...)
4) Point number should be preserved for "Fixed Point" systems.
5) Complete file sharing and record-locking for updates is enabled *if* DOS
"Share" is detected. Assuming Share *is* detected, QMX looks for "TCNODE"
in the DOS environment to determine the node number the user is on (i.e.
"SET TCNODE=2" for node 2, etc), and then uses BAT2MAIL.XRS, MAIL2IDX.XRS,
SUMMARY2.XRS, USER2.XRS & AREAS2.XRS, all of which get archived into the
file BAT2MAIL.* unless it's a local SysOp logon and SysOpOut is in affect.
Also: QMX will look for DORINFOx.DEF, and EXITINFx.BBS where 'x' = TCNODE
if file sharing is in effect (in other words DORINFO2.DEF & EXITINF2.BBS
for node 2). Multiple users can all access the databases at one time, but
NOTE: This assumes your BBS software supports multi-user file-sharing and
record-locking, which the current version (2.61) of QuickBBS does not, and
it further assumes your software puts the door info and exit info into the
above named files (or you copy it there for QMX)! Full support for the
"RemoteAccess BBS" software is included. QMX looks for *any* file with an
extension of ".RA" and if one is found, QMX becomes a chameleon and plays
like it is "RAX" (Remote Access eXpress) which in turn makes XRS 3.12 and
later tag the tear and origin lines with proper identities. Please see
Peter Jannsens' writeup and batch file examples for using QMX with Remote
Access in the included file "R_ACCESS.QMX". Note: native Dutch message &
help overlays for XRS (Peter and friends) and Dutch language documentation
by Rudi Kusters is available, making XRS truly bi-lingual, soon to become
multi-lingual! If you need Dutch language support for XRS, contact Peter
or myself for further details.
6) For new users, the "high message" is automatically set at the 80% position.
7) A 16-bit CRC of the user name is stored in binary form inside one of the
files. Any tampering with the name field or address fields will cause XRS
3.12 and later to bomb gracelessly with a security violation error.
8) A 16-bit CRC of the XORIGIN.XRS file (if present) is stored in binary form
inside one of the files. Any tampering with (or erasure of) the contents of
that file will cause XRS >= 3.12 to bomb with a security violation error.
9) New QMXSETUP.CFG parameter: "NoBeep" turns off beeps on SysOp side.
10) Unconfigured (new) users can only select "Configure" or "Quit". After
they configure message areas, then they can pack mail. (just selecting a
packing method and/or transfer protocol will not do!)
11) Maximum "LIMIT" parameter works - before it always allowed 995...
12) Smaller buffer for MSGTXT.BBS - runs faster.
13) Locked "Bottom-Line" bar with version #, user, point, level & baud rate.
Desqview is automatically detected, and the status-bar (Locked 25th line)
is *not* used, plus the hardware scrolling and line-deletion is turned off.
The net effect is that the program can run in a window without causing the
rest of your screen to scroll up (which can be confusing at best!).
14) "DSZ>NUL" in QMXSETUP.CFG is obsolete, so I removed support for it.
15) Swapped around PKZip, PKArc and LHArc and the "Good", "Better", "Best".
16) LASTREAD.BBS pointers are corrected - before I pointed to group + 1.
17) QMX only considers the default groups when determining the "Last Read".
18) I only update the LASTREAD.BBS pointers for groups that are selected.
19) Subject lines are shortened instead of space-filled at the end. This
takes up less space in both BATxMAIL.XRS and SUMMARYx.XRS, especially
important for showing large mailbag summaries on-screen with the <F6>
hot-key (they used to exceed 64k, now it is just about impossible -
the largest summary I can display is 65535 bytes, and the display of
it is simply truncated if it exceeds that).
20) QMX looks for FLSEARCH.QMX instead of .BBS - if not found *NO* "New
File Search" is done at all. This way you can just search one or two
if that is what you want, or you can turn it off altogether. If you
want it to work like before, just "COPY FLSEARCH.BBS FLSEARCH.QMX".
(the format of the file is *exactly* like FLSEARCH.BBS!)
21) New QMXSETUP.CFG parameter "OutPath x:\path" allows you to have QMX
automatically place the resulting BATxMAIL.xxx archive file into a
different subdirectory. The "X:\PATH" portion *MUST* point to a
directory name! (you can't change the final filename, anyway)
22) QMX says "Local" in place of "0 bps" in the bottom-line ID bar.